|
1
|
|
4
|
Save your configuration as described in the Saving Your Configuration chapter.
|
IMPORTANT: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.At least one administrative user account that has ECS functionality privileges must be configured on the system. This is the account that is used to log on and execute ECS-related commands. For security purposes, it is recommended that these user accounts be created along with general system functionality administration.
|
l
|
Aside from having ECS capabilities, an ECS Administrator account also has the same capabilities and privileges as any other system-level administrator account.
|
|
l
|
You can also create system ECS user account for a config-administrator, operator, or inspector. ECS accounts have all the same system level privileges of normal system accounts except that they have full ECS command execution capability. For example, an ECS has rights to execute every command that a regular administrator can in addition to all of the ECS commands.
|
|
l
|
Note that only Administrator and Config-administrator-level users can provision ECS functionality. Refer to the Configuring System Settings chapter of the System Administration and Configuration Guide for additional information on administrative user privileges.
|
To configure and enable ECS functionality on your system you must obtain and install the [600-00-7526] Enhanced Charging Bundle 1 1k Sessions license.
To configure and enable Diameter and DCCA functionality with ECS on your system, you must obtain and install the [600-00-7574] Enhanced Charging Bundle 2 1k Sessions license.
For information on installing licenses, see the Managing License Keys section of the Software Management Operations chapter in the Administration and Configuration Guide.
|
l
|
If you are using the Category-based Content Filtering application, refer to the Content Filtering Services Administration Guide for specific configuration procedures.
|
A charging service has analyzers that define which packets to examine and ruledefs (ruledefs) that define what packet contents to take action on and what action to take when the ruledef is true. Charging services are configured at the global configuration level and are available to perform packet inspection on sessions in all contexts.
|
1
|
|
4
|
|
10
|
Save your configuration as described in the Saving Your Configuration chapter.
|
IMPORTANT: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.A ruledef can be a charging or routing, or a post-processing rule. If the same ruledef is required to be a charging rule in one rulebase and a post-processing rule in another one, then two separate identical ruledefs will have to be defined.
|
l
|
For information on all the protocol types, expressions, operators, and conditions supported, refer to the Ruledef Configuration Mode Commands chapter of the Command Line Interface Reference.
|
|
l
|
The rule-application option specifies the ruledef type. By default, if not specified, the system configures the ruledef as a charging ruledef.
|
|
l
|
For information on all the protocol types, expressions, operators, and conditions supported, refer to the Ruledef Configuration Mode Commands chapter of the Command Line Interface Reference.
|
|
l
|
The rule-application option specifies the ruledef type. By default, if not specified, the system configures the ruledef as a charging ruledef.
|
|
l
|
For information on all the protocol types, expressions, operators, and conditions supported, refer to the Ruledef Configuration Mode Commands chapter of the Command Line Interface Reference.
|
A group-of-ruledefs enables grouping rules into categories, so that charging systems can base the charging policy on the category.
Readdressing of packets based on the destination IP address of the packets enables redirecting unknown gateway traffic to known/trusted gateways. This is implemented by configuring the re-address server in the charging action.
A rulebase specifies which protocol analyzers to run and which packets are analyzed. Multiple rulebases may be defined for the Active Charging Service. A rulebase is basically a subscriber’s profile in a charging service.
flow end-condition { { content-filtering | normal-end-signaling | timeout + } | { { hagr | handoff | session-end } [ flow-overflow ] + } [ url-blacklisting ] } edr <edr_format_name>
action priority <action_priority> { [ dynamic-only | static-and-dynamic | timedef <timedef_name> ] { group-of-ruledefs <ruledefs_group_name> | ruledef <ruledef_name> } charging-action <charging_action_name> [ monitoring-key <monitoring_key> ] [ description <description> ] }
route priority <route_priority> ruledef <ruledef_name> analyzer <analyzer> [ description <description> ]
|
l
|
When R7 Gx is enabled, “static-and-dynamic” rules behave exactly like “dynamic-only” rules. I.e. they must be activated explicitly by the PCRF. When Gx is not enabled, “static-and-dynamic” rules behave exactly like static rules.
|
ECS generates postpaid charging data files which can be retrieved from the system periodically and used as input to a billing mediation system for postprocessing.
Up to 32 different EDR schema types may be specified, each composed of up to 32 fields or analyzer parameter names. The records are written at the time of each rule event in a comma-separated (CSV) format.
attribute <attribute> { [ format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds } ] [ localtime ] | [ { ip | tcp } { bytes | pkts } { downlink | uplink } ] priority <priority> }
IMPORTANT: For information on EDR format configuration and rule variables, refer to the EDR Format Configuration Mode Commands chapter of the Command Line Interface Reference.ECS generates postpaid charging data files which can be retrieved from the system periodically and used as input to a billing mediation system for postprocessing.
UDRs are generated according to action statements in rule commands. Up to 32 different UDR schema types may be specified, each composed of up to 32 fields or analyzer parameter names. The records are written thresholds in a comma-separated (CSV) format.
attribute <attribute> { [ format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds } ] [ localtime ] | [ { bytes | pkts } { downlink | uplink } ] ] priority <priority> }
IMPORTANT: For information on UDR format configuration and rule variables, refer to the UDR Format Configuration Mode Commands chapter of the Command Line Interface Reference.To retrieve charging records you must configure the context that stores the charging records to accept SFTP connections.
|
l
|
You must specify the sftp keyword to enable the new account to SFTP into the context to retrieve record files.
|
IMPORTANT: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.This section describes how to apply an existing rulebase to a subscriber. For information on how to configure rulebases, see the Configuring Rulebases section.
Save your configuration as described in the Saving Your Configuration chapter.
This section describes how to configure an existing rulebase within an APN for a GGSN. For information on how to configure rulebases, see the Configuring Rulebases section.
Save your configuration as described in the Saving Your Configuration chapter.
This section describes how to configure the internal optimization level for improved performance when the system evaluates each instance of the action CLI command.
|
l
|
Both the medium and high options causes reorganization of the entire memory structure whenever any change is made (for example, adding another action CLI command).
|
|
l
|
high option causes allocation of a significant amount of memory for the most efficient organization.
|
|
l
|
Save your configuration as described in the Saving Your Configuration chapter.
|
This section describes how to configure the Prepaid Credit Control Application for Diameter or RADIUS.
IMPORTANT: To configure and enable Diameter and DCCA functionality with ECS on your system, you must obtain and install the [600-00-7574] Enhanced Charging Bundle 2 1k Sessions license.IMPORTANT: Before configuring Diameter or RADIUS CCA, you must configure AAA parameters as described in the AAA Interface Administration and Reference.|
1
|
|
3
|
Save your configuration as described in the Saving Your Configuration chapter.
|
IMPORTANT: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.Use the following configuration example to configure the Prepaid Credit Control Application for Diameter or RADIUS:
|
l
|
<service_name> must be the name of the Active Charging Service in which you want to configure Prepaid Credit Control Application.
|
|
l
|
<charging_action_name> must be the name of the charging action for which you want to configure Prepaid Credit Control Application.
|
|
l
|
Option. To configure the redirection of URL for packets that match a ruledef and action on quota request timer, in the Charging Action Configuration mode, enter the following command. This command also specifies the redirect-URL action on packet and flow for Session Control functionality.
|
flow action redirect-url "http://10.1.67.214/cgi-bin/aoc.cgi\077 imsi=#bearer.calling-station-id#&url=#http.url#&acctsessid=#bearer.acct-session-id#&correlationid=#bearer.correlation-id#&username=#bearer.user-name#&ip=#bearer.served-bsa-addr#&subid=#bearer.subscriber-id#&host=#http.host#&httpuri=#http.uri#" clear-quota-retry-timer
|
l
|
Option. To configure credit control quota related parameters, use the following configuration example:
|
cca quota { holding-time <holding_time> content-id <content_id> | retry-time <retry_time> [ max-retries <max_retries> ] }
cca quota time-duration algorithm { consumed-time <consumed_time> [ plus-idle ] [ content-id <content_id> ] | continuous-time-periods <seconds> [ content-id <content_id> ] | parking-meter <seconds> [ content-id <content_id> ] }
<rulebase_name> must be the name of the rulebase in which you want to configure Prepaid Credit Control configurables.
|
l
|
Option. To define credit control rules for quota state and URL redirect match rules with RADIUS AVP, use the following configuration example:
|
<ruledef_name> must be the name of the ruledef that you want to use for Prepaid Credit Control Application rules.
cca redirect-indicator configuration is a RADIUS specific configuration.
|
l
|
Option. This is a Diameter-specific configuration. To configure the failure handling options for credit control session, in the Credit Control Configuration Mode, use the following configuration:
|
failure-handling { ccfh-session-timeout <session_timeout> | { initial-request | terminate-request | update-request } { continue [ go-offline-after-tx-expiry | retry-after-tx-expiry ] | retry-and-terminate [ retry-after-tx-expiry ] | terminate }
|
l
|
Option. To configure the triggering option for credit reauthorization when the named values in the subscriber session changes, in the Credit Control Configuration Mode, enter the following command:
|
|
l
|
Option: This is a Diameter specific configuration. If the configuration is for 3GPP network, to configure the virtual or real APN name to be sent in Credit Control Application (CCA) message, in the Credit Control Configuration Mode, enter the following command:
|
IMPORTANT: To configure and enable Diameter and DCCA functionality with ECS on your system, you must obtain and install the [600-00-7574] Enhanced Charging Bundle 2 1k Sessions license.IMPORTANT: It is assumed that you have already fully configured the AAA parameters as described in the AAA Interface Administration and Reference, and Credit Control Application as described in Configuring Prepaid Credit Control Application (CCA) section for Diameter mode. diameter peer-select peer <peer_name> [ realm <realm_name> ] [ secondary-peer <sec_peer_name> [ realm <realm_name> ] ] [ imsi-based { [ prefix | suffix ] <imsi/prefix/suffix_start_value> } [ to <imsi/prefix/suffix_end_value> ] ]
|
l
|
Diameter peer configuration set with the diameter peer-select command can be overridden by the dcca peer-select peer command in the APN Configuration mode for 3GPP service networks, and in Subscriber Configuration mode in other service networks.
|
|
l
|
The specific Credit Control Group to be used for subscribers must be configured in the APN Configuration Mode using the credit-control-group <cc_group_name> command.
|
|
l
|
Option. To configure the maximum time, in seconds, to wait for a response from Diameter peer, in the Credit Control Configuration Mode, enter the following command:
|
diameter pending-timeout <duration>
|
l
|
Option. To configure Diameter Credit Control Session Failover, in the Credit Control Configuration Mode, enter the following command:
|
When enabled, in the event of failure, failure handling action is based on the failure-handling CLI.
|
l
|
Option. If you want to configure the service for IMS authorization in 3GPP service network, you can configure dynamic rule matching with Gx interface and dynamic rule matching order in rulebase, use the following configuration example:
|
action priority <action_priority> { [ dynamic-only | static-and-dynamic | timedef <timedef_name> ] { group-of-ruledefs <ruledefs_group_name> | ruledef <ruledef_name> } charging-action <charging_action_name> [ monitoring-key <monitoring_key> ] [ description <description> ] }
|
l
|
Option. To configure Diameter group AVP Requested-Service-Unit for Gy interface support to include a sub-AVP in CCRs using volume, time, and unit specific charging, in the Rulebase Configuration Mode, enter the following command:
|
cca diameter requested-service-unit sub-avp { time cc-time <duration> | units cc-service-specific-units <charging_unit> | volume { cc-input-octets <bytes> | cc-output-octets <bytes> | cc-total-octets <bytes> } + }
|
l
|
If the Diameter endpoint parameters are not yet configured, see the Configuring Diameter Endpoint section in the AAA Interface Administration and Reference for information on how to configure them.
|
IMPORTANT: The dcca peer-select configuration completely overrides all instances of diameter peer-select configured within the Credit Control Configuration Mode for an Active Charging service. dcca peer-select peer <host_name> [ [ realm <realm_name> ] [ secondary-peer <host_name> [ realm <realm_name> ] ] ]
IMPORTANT: The dcca peer-select configuration completely overrides all instances of diameter peer-select configured within the Credit Control Configuration Mode for an Active Charging service. dcca peer-select peer <host_name> [ [ realm <realm_name> ] [ secondary-peer <host_name> [ realm <realm_name> ] ] ]
RADIUS prepaid billing operates on a per content-type basis. Individual content-types are marked for prepaid treatment. When a traffic analysis rule marked with prepaid content-types matches, it triggers prepaid charge management.
IMPORTANT: The RADIUS Prepaid feature of ECS has no connection to the system-level Prepaid Billing Support or the 3GPP2 Prepaid features that are enabled under different licenses.Use the following configuration example to configure RADIUS Prepaid Charging with Enhanced Charging feature.
IMPORTANT: It is assumed that you have already fully configured the AAA parameters as described in the AAA Interface Administration and Reference, and Credit Control Application as described in Configuring Prepaid Credit Control Application (CCA) section for RADIUS mode. |
l
|
<rulebase_name> must be the name of the rulebase in which you want to configure Prepaid Credit Control configurables.
|
|
l
|
<vpn_context> must be the charging context in which the RADIUS parameters are configured:
|
|
l
|
Option. To specify the accounting interval duration for RADIUS prepaid accounting, in the Rulebase Configuration Mode, enter the following command:
|
cca radius accounting interval <interval>
|
l
|
Option. To specify the user password for RADIUS prepaid services, in the Rulebase Configuration Mode, enter the following command:
|
|
l
|
If RADIUS server parameters are not yet configured, configure them as described in the Configuring AAA Functionality section of the AAA Interface Administration and Reference.
|
User traffic is directed through the ECS service inspection engine by using Access Control List (ACL) mechanism to selectively steer subscriber traffic.
|
2
|
|
3
|
|
5
|
Save your configuration as described in the Saving Your Configuration chapter.
|
IMPORTANT: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.Use the following configuration example to create an ACL to use in steering subscriber traffic through ECS:
|
l
|
<service_name> must be the ACS service name; no CSS service needs to be configured.
|
IP ACLs are applied to subscribers via attributes in their profile. The subscriber profile could be configured locally on the system or remotely on a RADIUS server.
To apply an ACL to a RADIUS-based subscriber, use the Filter-Id attribute. For more information on this attribute, refer to the AAA Interface Administration and Reference.
context <context_name>
Use the following configuration example to apply an ACL to the default subscriber:
context <context_name>
context <context_name>
This section describes how to configure GTPP accounting which generates G-CDRs for ECS. Generated G-CDRs are sent to a configured Charging Gateway Function (CGF). ECS G-CDRs are sent in ASN.1 format and are encoded as described in 3GPP TS 32.015 V3.9.0 (2002–03) and 3GPP TS 29.060 V6.7.0 (2004–12).
IMPORTANT: If you have configured RADIUS accounting you do not need to configure GTPP accounting.|
l
|
The gtpp single-source command must be entered before any other configuration commands. If you add it to an existing configuration, make sure that it is the first command implemented after cards and ports are configured. This ensures that this command is implemented before any AAA Manager or Session Manager processes are started.
|
|
l
|
The GGSN has a concept of an accounting context. By default the accounting context is the context in which the GGSN service is configured. Make sure that you configure the GTPP charging agent and the GTPP accounting servers.
|
Save your configuration as described in the Saving Your Configuration chapter.
This section provides an example configuration to configure EDR/UDR file transfer and file properties parameters, including configuring hard disk support on SMC card on ST40 platform, transfer modes, transfer interval, etc.
cdr [ [ push-interval <interval> ] [ push-trigger space-usage-percent <trigger_percentage> ] [ remove-file-after-transfer ] [ transfer-mode { pull | push primary { encrypted-url <encrypted_url> | url <url> } [ secondary { encrypted-secondary-url <encrypted_secondry_url> | url <secondary_url> } ] } ] [ via local-context ] + | use-harddisk ]
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix <string> ] [ delete-timeout <seconds> ] [ directory <directory_name> ] [ edr-format-name ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [ name <file_name> ] [ reset-indicator ] [ rotation [ num-records <number> | time <seconds> | volume <bytes> ] ] [ sequence-number { omit | padded | padded-six-length | unpadded } ] [ storage-limit <limit> ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text <string> ] [ trap-on-file-delete ] [ xor-final-record ] +
file [ charging-service-name { include | omit } ] [ compression { gzip | none } ] [ current-prefix <string> ] [ delete-timeout <seconds> ] [ directory <directory_name> ] [ exclude-checksum-record ] [ field-separator { hyphen | omit | underscore } ] [ file-sequence-number rulebase-seq-num ] [ headers ] [ name <file_name> ] [ reset-indicator ] [ rotation [ num-records <number> | time <seconds> | volume <bytes> ] ] [ sequence-number { omit | padded | padded-six-length | unpadded } ] [ storage-limit <limit> ] [ time-stamp { expanded-format | rotated-format | unix-format } ] [ trailing-text <string> ] [ trap-on-file-delete ] [ udr-seq-num ] [ xor-final-record ] +
|
l
|
The cdr command keywords can be configured either in the EDR or the UDR Configuration Mode. Configuring in one mode prevents the configurations from being applied in the other mode.
|
|
l
|
The use-harddisk keyword is only available on the ST40 platform.
|
|
l
|
For the storage-limit <limit> keyword, on the ST16 platform, the total storage limit is 256 MB (268435456 bytes). And, on ST40 platform, the total storage limit is 512 MB (536870912 bytes). This limit is for both UDR and EDR files combined.
|
cdr-push { all | local-filename <file_name> }
|
l
|
Before you can use this command, the CDR transfer mode and file locations must be set to push in the EDR/UDR Module Configuration Mode.
|
|
l
|
The cdr-push command is available in the Exec Mode.
|
|
l
|
<file_name> must be absolute path of the local file to push.
|
To retrieve UDR or EDR files you must SFTP into the context that was configured for EDR or UDR file generation with the FTP enabled account that you configured in the Enabling Charging Record Retrieval section.
The following commands use SFTP to log on to a context named ECP as a user named ecpadmin, through an interface configured in the ECS context that has the IP address 192.168.1.10 and retrieve all EDR or UDR files from the default locations:
IMPORTANT: This is a customer-specific feature. Please contact your sales representative for more information.|
1
|
Create/configure a ruledef to identify the HTTP packets in which the x-headers must be inserted. For information on how to create/configure ruledefs, see the Configuring Charging Rule Definitions section.
|
|
2
|
Create/configure a rulebase and configure the charging-action, which will insert the x-header fields into the HTTP packets. For information on how to create/configure rulebases, see the Configuring Rulebases section.
|
|
5
|
|
6
|
Save your configuration as described in the Saving Your Configuration chapter.
|
insert <xheader_field_name> { string-constant <xheader_field_value> | variable { bearer { 3gpp charging-id | ggsn-address | imsi | radius-calling-station-id | sgsn-address | sn-rulebase | subscriber-ip-address } | http { host | url } }
Use the following configuration example to configure a charging action for insertion of x-header fields:
This section describes how to configure the Post-processing feature to enable processing of packets even if rule matching for them has been disabled.
action priority <action_priority> { [ dynamic-only | static-and-dynamic | timedef <timedef_name> ] { group-of-ruledefs <ruledefs_group_name> | ruledef <ruledef_name> } charging-action <charging_action_name> [ monitoring-key <monitoring_key> ] [ description <description> ] }
|
l
|
In the Rulebase Configuration Mode, the ruledef configured for post-processing action must have been configured for post processing in the Ruledef Configuration mode.
|
|
l
|
If the same ruledef is required to be a charging rule in one rulebase and a post-processing rule in another one, then two separate identical ruledefs will have to be defined.
|
|
l
|
Save your configuration as described in the Saving Your Configuration chapter.
|
|
l
|
In this release, delay charging with dynamic rules is not supported, hence there cannot be dynamic post-processing rules.
|
This section describes how to configure the Time-of-Day Activation/Deactivation of Rules feature to enable charging according to day/time.
Use the following configuration example to configure the Time-of-Day Activation/Deactivation of Rules feature:
start day { friday | monday | saturday | sunday | thursday | tuesday | wednesday } time <hh> <mm> <ss> end day { friday | monday | saturday | sunday | thursday | tuesday | wednesday } time <hh> <mm> <ss>
action priority <action_priority> timedef <timedef_name> { group-of-ruledefs <group_name> | ruledef <ruledef_name> } charging-action <charging_action_name> [ description <description> ]
|
l
|
If for a timeslot, “start time” > “end time”, that rule will span the midnight. I.e. that rule is considered to be active from the current day till the next day.
|
|
l
|
If for a timeslot, “start day” > “end day”, that rule will span over the current week till the end day in the next week.
|
|
l
|
In the following cases a rule will be active all the time:
- a timedef is not configured in an action priority - a timedef is configured in an action priority, but the named timedef is not defined - a timedef is defined but with no timeslots |
This section describes how to configure the URL Filtering feature to simplify rules for URL detection.
show active-charging group-of-prefixed-urls { all | name <group_name> } [ service name <acs_service> ] [ | { grep <grep_options> | more } ]
